Hello Infinispan users,

What ? You’re wondering where Beta1 is ? And what happened to 9.4.7 ? Unfortunately, those releases, while tagged and available on your closest Maven Central mirror will only work with Java 11, so we had to rebuild and re-release.

So, without further ado, I give you 10.0.0.Beta2 and 9.4.8.Final.

The first change I should outline is one that will impact you if you are building Infinispan from source. The previous build structure required having both JDK 8 and JDK 11 in order to compile a release which worked on both. In order to simplify the build process, as well as ensuring that the output is always consistent we now require Java 11 only. Don’t worry: the resulting binaries will still work on Java 8 and greater.

Dear Infinispanners,

The C++ and C# 8.3.0.Beta1 releases are available!

Main feature for this release is: transactions. Clients can now run sequence of hotrod operations in a transactional way. Basic methods are provided to begin, commit or rollback a transaction over an hotrod connection (hotrod 2.7 and Infinispan 9.3+ are required). API are quite easy to use:

Source code, binaries and docs are at the usual place. Thank you for following us! The Infinispan Team

Release notes [2] https://github.com/infinispan/cpp-client/tree/8.3.0.Beta1[C code for 8.3.0.Beta1] [2#] C# code for 8.3.0.Beta1

Infinispan users,

We have just released 9.3.0.Beta1 which includes 38 fixes. Highlights of this release include:

Conflict Resolution Improvements

Reactive Streams based Cache Loader SPI available

Infinispan can now be built and tested with Java 10/11

Max Idle expiration is now cluster-wide including events

The Java Hot Rod client can handle data in multiple formats

Improved merge after long GC pauses avoiding data loss

Admin console supports counters in standalone mode

Lots of bug fixes, test fixes, and documentation improvements

As usual, you can find all the bits on our website. If you find any issues, don’t hesitate to report them on our issue tracker.

Enjoy, The Infinispan Team

Dear Infinispanners, C++ and C# 8.2.0.Beta1 releases are available!

These releases contain all the 8.2.0 features.

Worth a mention is the improvement in the remote execution API: we moved the JBossMarshaller basic implementation from test to the distro in order to simplify the data management on the application side. Test examples

Next step will be a CR release containing improvements on API docs (doxygen)

Check the release notes, browse the source code (C++, C#) or download the releases!

Cheers, The Infinispan Team

It’s release day at Infinispan HQ and we’ve just released a couple of new versions:

Infinispan 9.0.0.Beta2 includes:

New:

Backwards compatibility:

Full release notes.

Infinispan 8.2.6.Final includes multiple bug fixes.

Cheers,

Galder

We’ve just released Infinispan 7.2.0.Beta2 which adds better support for determining which configuration options have been defined by the user versus those options that contain default values. This is an important stepping stone in our aim to enable partial configuration overlays and proper configuration template support.

On top of that, we’ve added the capability for Java Hot Rod clients to recover from full cluster restarts and fixed an important topology transfer bug that lead to ArrayIndexOutOfBoundsException exceptions when applying topology changes.

Finally, in order to provide better out-of-the-box experience with Near Caches in Java Hot Rod client, we have made mandatory to define the maximum number of entries Near Caches should have. Previously, Near Caches were configured to be unbounded by default which would have resulted in memory leaks unless the client removed them by calling RemoteCache.remove() or similar. A configuration exceptions is reported now if no maximum size has been defined in the Java Hot Rod client, but the user can still provide a 0 or negative value to indicate the Near Caches should be unbounded.

For a complete list of features and bug fixes included in this release, please refer to the release notes.  

Feel free to join us and shape the future releases on our forums, our mailing lists or our #infinispan IRC channel.

Cheers,

Galder

The first beta version of the Infinispan native python client to connect to the Infinispan Hot Rod servers is available now from Infinispan’s GitHub repository or PyPi. Please check the latest README information to find out more about installation instructions.

So, what’s in it? For this first beta release, we’ve implemented all the operations available in the Hot Rod specification and they’ve been tested with string inputs. This release does not include code to deal with client intelligence superior to 1, so clients cannot receive notifications of cluster changes nor can they locate data in an intelligent manner by applying consistent hash algorithms to the keys. These capabilities, plus further examples such as how to integrate with payloads from Google Protocol Buffers will come in next beta releases.

If you’re looking for code examples for the Infinispan Python client, you can find a very basic one in the README file itself, or check the testsuite within the source package. In next releases we’ll be creating a wiki with more detailed examples.

As always, if you have any doubt please use the user forums and for any bugs or feature requests, please log them via JIRA.

Cheers, Galder

I’ve just released the long-awaited first beta of Infinispan 4.2.0, codenamed Ursus.  The blocker that’s been keeping Ursus in Alpha for so long - ISPN-180 - is now complete and ready for you to take out for a spin.  Thanks to the work put in by Mircea and Vladimir, ISPN-180 adds support in the distribution algorithm to detect whether Infinispan instances are co-located on the same physical server (or even the same rack) and pick secondary owners of data with this knowledge in mind. This helps ensure maximum durability of data, so if physical machines - or even an entire rack - were to fail, data is not lost.  For more details on ISPN-180, have a look at this wiki page which details its use.

The JOPR/RHQ plugin now works in multi cache manager environments (ISPN-675) and thanks to ISPN-754, cache manager instances can be easily identified when using the JOPR/RHQ management GUI.  As a result of ISPN-754, JMX object names follow best practices as set up by Sun/Oracle and so this means that object names exported to JMX have changed from this version onwards. See this wiki page for detailed information.

For a list of all fixes since Alpha5, have a look at the release notes in JIRA, and as always, download the release here, and let us know what you think using the user forums.

Onward to release candidate and final release phases!  :-)

Enjoy, Manik